                              ===========================                             
                              R E L E A S E    N O T E S
                              ===========================

                         QLogic 5709 NC-SI Firmware

                      Copyright (c) 2015 QLogic Corporation
                                 All rights reserved.


Known issues
============


History
=======
Version 2.0.13 Jul 30, 2013
================================
			
	Fixes:
	-------------

	1.	Problem:	CQ70391 - 5709 ncsi firmware hang causes bootcode to fail
                    TOE handshake with OEM BIOS.

		Cause:	 	FW spinwait for available tx descriptor. That creates
                    a deadlock since same process is responsible for freeing the descriptor.

		Fix:		Instead of spinwait, just check for available tx descriptor,
                    If not available, suspend transmission and try again later.

Version 2.0.12 Jul 26, 2011
================================
			
	Fixes:
	-------------

	1.	Problem:	CQ54461 - System may hang running PXE reboot loop test.

		Cause:	 	FW enables hardware block using misc commmand register. 
                    The read operation hits the window during which PXE 
                    driver is resetting the port. As a result, some common 
                    hardware block is left in a pending state servicing
                    one function. This prevents further GRC access to 
                    the other function.

		Fix:		Use a different register to enable hardware blocks.

Version 2.0.11 Jan 17, 2010
================================
			
	Fixes:
	-------------

	1.	Problem:	CQ49357 - Incorrect reason code for unknown command type

		Cause:	 	FW check command length first before checking command type 
		            validity

		Fix:		Fix NCSI command validation order.

	2.	Problem:	CQ49298 and CQ49303 - Link setting and Flow control not correct in Get NCSI
                    Parameter Command
                    
		Cause:	 	Parameter not updated correctly in FW

		Fix:		Fix NCSI FW bug.

	3.	Problem:	CQ49358 - Total Rx pkt statistics not correct in Get NCSI
                    Statistics Command
                    
		Cause:	 	Statistics not updated correctly in FW

		Fix:		Fix NCSI FW bug.

	3.	Problem:	CQ52341 - IP communication lost for multiple package in VAUX mode
                    
		Cause:	 	HW arbitration register is confirgured before Package ID is assigned.

		Fix:		Fix NCSI FW bug.


Version 2.0.10 June 1, 2010
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ48087 - SoL/Ckvm not ready using ncsi 2.0.9

        Cause:      sol/ckvm not ready.  

        Fix:        A typo was introduced accidentally in last release.

Version 2.0.9 May 24, 2010
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ47486 - Management traffic lock up.

        Cause:      Unexpected "error" frames are causing some fifo 
        underflow condition in the firmware. That occasionally will stop 
        egress traffic processing from BMC.  

        Fix:        FW is detecting such fifo underflow condition and 
        reset the fifo accordingly.


Version 2.0.8 Mar 10, 2010
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ46415 - Unable to open up management GUI.

        Cause:      Issue introduced based on regression change from v2.0.7.

        Fix:        Corrected improper code


Version 2.0.7 Mar 2, 2010)
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ46152 - Some MAC to BIOS mac get rejected.

        Cause:      Incorrect logic for MAC validation.

        Fix:        A bit-wise AND needs to be replaced with a bit-wise OR.

Version 2.0.6 Dec 7, 2009)
================================
            
    Fixes:
    -------------

    1.  Problem:    Customer reports VLAN tagged packets being dropped when run with latest OEM router              
                    OS.

        Cause:      Router is inserting non zero PRI value into packets, and these are being dropped by 
                NCSI MFW because they do not match the value programmed by the BMC.

                Unlike UMP, NCSI allows for filtering on PRI in addition to VID, and this has been
                supported by NCSI MFW from the first release.

        Fix:        Near term fix is to disable support for this feature, and long term support is to 
                address in the DMTF and define better support for it so it can be enabled, disabled,
                etc.

Version 2.0.5 Oct 7, 2009)
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ 43503, 43550, 43601, 43623 all dups for 42757 in prev release.

        Cause:      This problem continues to defy a rootcause, and was not addressed afterall
                in the previous release.   NCSI Command previous response packet processing 
                seems to be related to the issue, and avoiding it seems to avoid the issue.
                FW and has been modified to simply reexecute duplicate commands.

        Fix:        Temporary work around for t5.0a to allow more time to rootcause the issue.


Version 2.0.4 Sept 4, 2009)
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ 42757-NCSI stop passing traffic after BACS test.

        Cause:      Debugging shows multiple influences in the problem, some external to NCSI FW.
                Debugging also revealed previous change, while not directly causing problem, has
                effect, and when rolled back, prevents problem from occurring.  This will be use
                as a temp work around until full problem is resolved.

        Fix:        NCSI Command packet descriptor resource count needs to be used to specify
                count of NCSI TX Packet descriptor resources.  Previous change rolled back
                so counts are dependent.


Version 2.0.3 June 17, 2009)
================================
            
    Fixes:
    -------------

    1.  Problem:    CQ 41847-NCSI client and host stop passing traffic after driver load/unload test.

        Cause:      NCSI MFW experienced an MCP halt due to a bad data access that was eventually 
                found to be caused by attempting to reference from a bad pointer.  It was determined
                that was caused by the current RX design that has shared RX flags, but port specific
                tpbuf resources.  When the port reset occurred on driver load, the port resources
                were cleared, but not flags.

        Fix:        When port reset occurs, check if RX DMA is active for port being reset.  If so, give
                DMA time to get pkt out of RX FIFO, the clear RX flags and port resources.

Version 2.0.2 May 15, 2009)
================================
            
    Enhancements:
    -------------

    1.  Description:    Release new build to take advantage of shared NCSI protocol source code that was modified
                        for Everest build to add support for correctly reporting OEM specific link speeds in the
                        OEM link speed field of the Get Link Status command response payload.  This functionality 
                        was not present before.

        Impact:         Support for reporting OEM specific link speeds is now present, and functioning.  Currently 
                        the only OEM specific link speed is 2.5 Gb.  Forced links are reported as a value of 1 for
                        2.5Gb Half Duplex, and negotiated links are reported as a value of 2 for 2.5Gb Full Duplex.

Version 2.0.1 April 15, 2009)
================================
            
    Fixes:
    ------

    1.  Problem:    CQ 40447 - No connection to BMC with NCSI 2.00.

        Cause:  NCSI module had debug code left in that was returning control to dispatcher.

        Fix:        Remove line of debug code.

    Enhancements:
    -------------

    1.  Description:    Changed approach to MFW enabling required HW block when driver is loaded
                    to avoid potential synch issues.

        Impact:     MFW will not enable blocks when loading in driver present scenario, but will depend
                    upon driver to ensure blocks are enabled before MFW is allowed to execute.  


Version 2.0.0 March 23, 2009)
================================
            
    Enhancements:
    -------------

    1.  Description:    Approach to code sharing, and image building has been reorganized 
                to reduce the size of each build so the Xinan NCSI build will fit 
                into shared memory, especially with the dual media supporting 
                bootcode.

        Impact:     This release file contains only NCSI MFW for the Xinan family of chips.
                
                Xinan and Everest source trees will now be built and released separately
                from one another.  The release build will no longer be a chip specific
                image combined with the common image, but will be a single monolithic
                image.  This change will require support from XDIAG and Xinan BOOTCODE.
        
    2.  Description:    Added UMP based raw packet loopback feature to NCSI FW that 
                was not fully ported from UMP.

        Impact:     When feature is enabled in NVRAM, MFW will come up following
                POR with loopback/echo mode enabled.  While in this mode, the
                MFW will accept non NCSI control packets on the UMP RX interface
                and simply send them back out via the UMP TX interface.

                This mode applies to the whole package, not a port or channel.
                Multiple packages can have loopback enabled at once, but this 
                will require all packages have the HW Arb pins connected for 
                correct operation. Each package will sign the loopback packets 
                by depositing a signature in the final data word looped back in 
                the form 0x8874000x where x is the package ID.  This will allow
                a BMC to ID traffic looped back from each package if needed.

                NCSI MFW will exit the loopback mode if ANY NCSI control packet
                with ethertype 0x88F8 is seen on the RMII bus.  Once the mode
                has been terminated it will remain off until the next POR based
                MFW load event.

    3.  Description:    Reworked all reset handling code to streamline, and improve
                handling of reset channel command.

        Impact:     None

Version 1.0.6 Feb 2, 2009)
================================
    Fixes:
    ------

    1.  Problem:    CQ 39414 NCSI/5709: HW malfunction BSOD when running reboot test with iscsi initiator sw.

        Cause:      NCSI initialization exposed an issue where RV2P is placing a packet into an uninitialized context, 
                    resulting in BSOD.

        Fix:        Work around in MFW by not enabling EMAC block on port reset when driver present.


Version 1.0.5 Jan 13, 2009)
================================
    Fixes:
    ------

    1.  Problem:    CQ 37800 NCSI/57710: Sending Get Link Status command causes FW to stop
                    responding.

        Cause:      Command was not fully implemented in the Everest NCSI FW.

        Fix:        Provide full support for the command.

    2.  Problem:    CQ 37830, 57710 AEN reports incorrect value.
        
        Cause:      Using wrong definition.

        Fix:        Use correct definition.

    2.  Problem:    CQ 37876, 57710, no NCSI traffic after iSCSI boot to Win 2k3 image.
        
        Cause:      DMA Ops were failing to complete because UMP block not fully reset after
                    NIG reset.

        Fix:        Reset UMP block on NIG reset.


Version 1.0.4 Dec 18, 2008)
================================
    Fixes:
    ------

    1.  Problem:    CQ 38952 NCSI/5709: LOMs failing to respond to NCSI commands when shared 
                    LOM modes are changed.

        Cause:      NCSI FW was not clearing active pkt count when processing channel resets.
                    Sometimes this field was left non zero, which in rare situations, caused
                    resources to be de allocated twice causing pkt count to go negative and
                    stall the egress pipe.

        Fix:        Clear the field when processing channel reset.

    2.  Problem:    CQ 38855, cKVM remote console session unexpectedly closes during linux/windows 
                    driver load/unload.
    
        Cause:      Duplicate for CQ38952.

    3.  Problem:    CQ 38905, Lose network connection (ncsi to bmc ip and host ip) after trying 
                    to open OEM webpage when linux driver is up.
    
        Cause:      Duplicate for CQ38952.


Version 1.0.3 Oct 20, 2008)
================================
    Fixes:
    ------

    1.  Problem:    CQ 37958 NCSI/5709: Unable to login into iSCSI target when NCSI is 
                    enabled on 5709.

        Cause:      NCSI FW was using incorrect index to clear PM filter fields following 
                    resets.

        Fix:        Correct the index.

    2.  Problem:    CQ 37374 NCSI/57710-PQA reports Arp packets not being pass through on Everest/NCSI..

        Cause:      everest implementation of the MCP FTQ status bits does not match the 
                    original bit definition.

        Fix:        pkt qualifications performed when pkt at top of MCP FTQ was pushed into 
                    HW lib modules and made more chip specific to overcome incorrect packet 
                    filtering based on MCP FTQ status word that was causing ARP pkts to be dropped.

    3.  Problem:    CQ 37784 NCSI/5709-PQA reports no connection to bmc on OEM platform after 
                    connecting last LOM.

        Cause:      Duplicate for CQ 37530 described below.

        Fix:        Problem has been resolved by other changes to NCSI FW.  

    4.  Problem:    CQ 37520 NCSI/5709: PQA reports NCSI traffic stops after running BACS 
                    diagnostics.

        Cause:      Port reset is performed after each test within BACS diagnostic as means to 
                    "clean up", but NCSI port reset handling code was not resetting all required
                    resources.

        Fix:        Modify NCSI port reset code to reset all NCSI shared resources as well as 
                    port specific ones.

    5.  Problem:    CQ 37793 NCSI/57710: PQA reports PXE banner takes up to 90 seconds to appear
                    when NCSI FW is loaded.

        Cause:      NCSI FW executes in fixed 5ms timeslice that was starving bootcode on PXE load.  

        Fix:        Allow NCSI FW to return control to bootcode before completion of full timeslice
                    if there are no event indications to be processed.

    6.  Problem:    CQ 37804 NCSI/5709: PQA reports that NCSI FW returns incorrect Driver Status 
                    value after disabling driver.

        Cause:      Bit definitions were imported from UMP during initial port, and not updated.

        Fix:        Corrected bit definitions to be NCSI specific.

    7.  Problem:    CQ 37530 NCSI/5709: PQA reports that TOE and iSCSI hw key license behavior is 
                    incorrect when NCSI FW is enabled.

        Cause:      UMP ARB Control register not programmed correctly for multi LOM configurations.
                    Requires correct package ID, ARB timeout, and workaround for XON flowcontrol bug.

        Fix:        Modified both Everest and Xinan library modules to ensure register is programmed
                    correctly.

    8.  Problem:    As a follow on to CQ 37530, PQA now reports excessive bootup latency when NCSI FW 
                    that includes problem #7 fix is enabled.

        Cause:      Portions of all NCSI modules were redesigned to address problem #2 described above.  
                    Code was changed to perform blocking poll on register that should not block, but
                    this turned out to be a problem.

        Fix:        Reverted code to using method of non blocking polling for UMP Write Control Register.

    Enhancements:
    -------------

    1.  Description:    Integrated Everest NCSI module with latest shared bootcode files.

        Impact:         Everest NCSI FW v1.0.3 requires Everest Bootcode v4.6.2 or later.


Version 1.0.2 Sept 5, 2008)
================================
    Fixes:
    ------

    1.  Problem:    PQA reports incorrect value used to report OS absent in AEN pkt.

        Cause:      Incorrect definition.

        Fix:        Correct the definition to use 0, and not 2, for reporting OS absent.

    2.  Problem:    CQ 37092-PQA reports latest NCSI FW becomes unresponsive following 
                    pkt forwarding event.

        Cause:      Previous change resulted in pkt forwarding code incorrectly accessing
                    channel ID.

        Fix:        Use correct method for accessing channel ID.  See enhancement below.

    Enhancements:
    -------------

    1.  Description:    Adopt uniform method for Tx Module to access pkt channel ID in
                        TX Pkt Desc for all pkt types being sent to the BMC.  Previously, 
                        channel Id was accessed based upon pkt type, which resulted in 
                        errors in previous releases.

        Impact:         Command module now stores channel ID in TX Pkt Desc header when
                        queuing NCSI AEN and command Response pkts.  TX Module now accesses
                        channel ID exclusively from the TX Pkt Desc header for all pkts.        

Version 1.0.1 Aug 28, 2008)
================================
    Fixes:
    ------

    1.  Problem:    PQA reports no host traffic flows when run with latest NCSI FW.

        Cause:      Compatibility of common module with both Xinan and Everest chips 
                required change to how NCSI FW checks driver load status by storing
                local indicator.  The update if this indicator is done on every 
                FW invocation, but was being performed following the logic that handles 
                the port specific reset events.  Port specific reset handling code
                consults this indicator to determine whether the driver is loaded or
                not, and this caused stale data to be used in setting up the pkt
                forwarding configuration to go to the BMC only.

        Fix:        Establish current driver load state prior to handling port resets.

    2.  Problem:    PQA reports latest NCSI FW becomes unresponsive following AEN events.

        Cause:      Previous change resulted in AEN forwarding code using bad index, which
                created an invalid ptr, which caused a bad memory access which resulted 
                in locking up cpu.

        Fix:        Ensure required index is initialized.


Version 1.0.0 Aug 16, 2008)
================================
    Enhancements:
    -------------

    1.  Description:    Beta release of support for Everest 57710 chip.

        Impact:         See below.
        
    2.  Description:    Alpha release of support for Everest 57711 chip.

        Impact:         Enhancements 1 & 2 required a number of changes be made to the common and 
                        xlib modules to provide for commonality across all NCSI FW. These changes 
                        included the following:
                        
                        a) Added support for receiving and validating commands without the plus 2 byte 
                            alignment, and for sending responses that do not have the plus 2 byte alignment.

                        b) Modified common module approach to acquiring L2 stats that are reported to BMC 
                            via NCSI command.

                        c) Altered common module load point to support Everest Bootcode.

                        d) Altered approach to determining driver present status.

    3.  Description:    Modified timeslice calculation code to work correctly.

        Impact:         5ms timeslice is upheld.

    4.  Description:    Temporarily disabled optional checksum support pending update in DMTF.

    5.  Description:    Modified delay calculation code to work correctly.

        Impact:         Microsecond delay calc works correctly.

    6.  Description:    Modified init code to ensure previous state of HW arb is restored following reset.

        Impact:         State of HW arb feature is retained through soft resets.

    7.  Description:    Modified init code to ensure reset type is correctly determined.

        Impact:         FW will now correctly reinit as required following resets.

    8.  Description:    Modified macro used for driver presence status to function per channel.

        Impact:         Driver presence is now evaluated on a per channel basis.


Version 0.5.8 May, 2008)
================================
    Fixes:
    ------

    1.  Problem:    CQ 35489 Customer reports that Max sized VLAN tagged packet not being forwarded.

        Cause:      NCSI FW was was not including the VLAN tag size in the max pkt size check.

        Fix:        Modified code to include +4 bytes in max size if VLAN enabled.  

Version 0.5.7 May 6, 2008)
================================

    Fixes:
    ------

    1.  Problem:    Customer reports that multiLOM system ceases to pass NCSI traffic following a reset.

        Cause:      NCSI FW was zeroing out the default ARB Master timeout that is required to ensure
                correct ARB Master selection.

        Fix:        Modified code to not overwrite default value.   

    Enhancements:
    -------------

    1.  Description:    Added manual statistics accumulation logic to Everest NCSI HW module. Modified
                Xinan HW Module to maintain consistency in the common module.   

        Impact:     Now the common module uses a routine "NcsiCmdLib_Get_Updated_Statistics" with
                a common interface, that is exported by both HW modules.


Version 0.5.0 (Apr 29, 2008)
================================

        Fixes:
    ------

    1.  Problem:    CQ34757.  Packets were being lost on second port.

        Cause:      NCSI FW was using faulty OS Present MACRO to determine whether to enable mgmt pkt forwarding
                via the RX Parser allowing it to mistakenly enable this on the second port while the driver
                was loaded.

        Fix:        Fixed Driver loaded state macro.    

    2.  Problem:    PQA reports loss of NCSI connection after running stress test.

        Cause:      Egress pkt completion code was clearing "RX DMA IN PROGRESS" flag just before entering 
                routine to enqueue TAS FTQ record.  However, when the host is also stressing egress traffic,
                this TAS FTQ enqueue operation my be held off, and remain pending.  There is a flag to note
                this condition, but the rx in progress flag gates these attempts, so the operation could 
                never complete once that flag was cleared.

        Fix:        Clear all flags after TAS FTQ operation completes.

    3.  Problem:    CQ34927.PQA reports that host chariot traffic stalls when running to both host and NCSI.

        Cause:      NCSI firmware was overwritting the TPBUF address used to arm the DMA operations causing 
                mgmt pkts to be written into the host's portion of TPBUF.  This resulted from an intentional
                change that was not implemented completely.

        Fix:        Complete the implementation of the change returning status of TPBUF allocation operation.

    4.  Problem:    CQ34266.  iSCSI boot failed to get IP for second port when NCSI is running.

        Cause:      The original problem reported here was caused by #1 above.  However, resolving that issue
                exposed another issue that prevented both ports from getting IP during iSCSI boot.  In 
                essence, a silent HW interrupt (port specific reset) was occurring after the mgmt FW had
                started trying to initialize the TAS data pipe, and this prevented the HW event notification
                that the FW polls on from ever occurring because the HW blocks were then all disabled.  This 
                caused the FW to loop forever.

        Fix:        The fix is to note that the TAS init has failed, ignore it, and return control to bootcode.
                Because this was an interrupt, the bootcode will handle it once it can run, and will then
                report to the FW that a port specific reset occurred, thereby causing mgmt FW to initialize
                once more.  FW also does so if its error flag is still set.

    5.  Problem:    Customer developing NCSI reported that NCSI FW was not working with their RMII based BMC.

        Cause:      Apparently, the chip was browning out during Vaux because all chip blocks were being enabled 
                because mgmt FW was seeing false indications of PCI main power being present while in Vaux.

        Fix:        The real problem is in the customer's HW, but we were able to help them get past this by
                disabling a line of code in the mgmt FW init that enables all chip blocks if PCI main power
                is present.

    6.  Problem:    PQA reports that the Set Link command will not allow the link to be put back into AN mode
                after being forced from the advertised settings.

        Cause:      The bootcode is not fully honoring the set link request it is receiving from mgmt FW.

        Fix:        Temporary workaround is to set the "phy reset" bit in the netlink version of the set link 
                request, and this will return the phy to its default settings.

    Enhancements:
    -------------

    1.  Description:    Modified the set link command processing to allow support of common bootcode for UMP 
                and NCSI code on Xinan.

        Impact:     FW must map the NCSI set link config word to the netlink version supported by BC.

    2.  Description:    Restored NCSI token to version string as requested.

        Impact:     Tools that use the mgmt fw version string can now expect the "NCSI" token.

    3.  Description:    Altered the time at which the rx mgmt pkt cntl is enabled from doing so by default at
                load to doing so only when the channel is enabled by the BMC.

        Impact:     In OS absent, enabling by default meant that the Rx Parser was filtering and forwarding 
                pkts even if the channel was disabled.  Now it will not filter pkts until the BMC enables 
                the channel.

    4.  Description:    Added some additional error state and pkt statistics recording for internal use.

        Impact:     FW maintains state and stats for conditions not covered by existing NCSI statistics.

    5.  Description:    Fixed problem with determining cold verses warm and channel verses global reset status, 
                and associated init issues.

        Impact:     FW correctly determines the type of each reset that caused the most recent reload.

    6.  Description:    Modified controller statistics retrieval code to only return stats in OS present.  This
                is because the HW cannot be assured to work as required unless the driver is loaded.

        Impact:     0xFFFFFFFF will be returned for all stat values when Get I/F statistics command is 
                sent while OS Absent. 

    7.  Description:    Eliminated unneeded error handling code.
        
        Impact:     None.                                                              


Version 0.4.6 (Mar 18, 2008)
================================

    1.  Problem:    Egress packet traffic pass through halts.
    
        Cause:      Test packets with random pattern are initially matched as cmds because of 
                    0x88f8  value in specific location.  When found to not be commands, packets 
                    were not handled correctly leaving fw in invalid state and unable to pass
                    additional traffic.

        Fix:        Better discriminate potential command packets on rx, and clear state when
                    dropped.

    2.  Problem:    Egress packet traffic pass through halts.

        Cause:      Unable to allocate egress buffer resources.

        Fix:        Modify buffer deallocation logic to handle specific case.


Version 0.4.5 (Mar 10, 2008)
================================

    Fixes:
    ------

    1.  Problem:    Pass through fails to continue after driver unload.
    
        Cause:      Loss of state on driver load and unload caused by extraneous code.

        Fix:        Remove code.

Version 0.4.4 (Mar 7, 2008)
================================

    Fixes:
    ------

    1.  Problem:    Get I/F statistics command intermittently failing
        
        Cause:      Incorrect use of HC in preOS state.

        Fix:        Change approach used to force a coalesing of stats.

    2.  Problem:    Package selection commands rejected
    
        Cause:      Invalid instance id check.

        Fix:        Include package selection commands in instance ID check.


Version 0.4.3 (Feb 15, 2008)
================================

    Fixes:
    ------
    1.  Problem:    Valid egress packets to get dropped when channel enabled.

        Cause:      Same MAC address was programmed on both channels with the first 
            disabled and second enabled.  The order in which channel states 
            were examined during SA filtering caused valid egress packets to 
            be dropped on the disable channel instead of passing on enabled 
            channel.

        Fix:        If source MAC address match found on disabled channel, continue to
            check remaining channels for match on an enabled channel before 
            dropping the packet.


Version 0.4.1 (Feb 8, 2008)
================================

    Fixes:
    ------
    1.  Problem:    Reason code 0x9 returned in response to sending Set Flow Control 
            command with both enable bits set. 

        Cause:      Incorrect bit mask used.

        Fix:        Use correct bit mask.


Version 0.4.0 (Jan 29, 2008)
================================

- OEM command (GET NCSI parameters) - problem: no response 
- SET MAC - problem: with mac of zeros returned incorrect reason code
- RESET CHANNEL - problem: incorrect payload length
- OEM command (MODIFY HOST MAC) - problem: no response
- PACKAGE SELECT/DESELECT: problem: no response with Ch.ID = 0x1f
- PACKAGE SELECT/DESELECT: problem: package select followed by package deselect returns response/reason 0x01,0x01
- DISABLE CHANNEL - problem: incorrect payload length
- GET NCSI PARAMETERS - problem: no response
- SET LINK - problem: Set link to AUTO returns incorrect response/reason code
- BROADCAST FILTERING: problem: dhcp client = no pass-through; dhcp server = All broadcast pass-through; netbios = no pass-through
- GET PARAMETERS: problem: in reponose packet, 2 extra bytes before mac address


Version 0.3.0 (Sept 10, 2007)
================================

Initial Beta Release.


